Description of the data generated by an ANM import

ANM files can only be read into an empty network. PuT data cannot be read in at present.

The following description explains what network data that will be saved in Visum when importing ANM data.

ABSTRACT NETWORK MODEL

An *.anm file contains the XML root element <ABSTRACTNETWORKMODEL>. The following elements of the root element are used in Visum.

ANM

Visum

VERSNO

---

FROMTIME

---

TOTIME

---

NAME

Name under file info

Note

After an ANM import, in menu File > File info, you can find the name and the path of the read in file, as well as the date and the time of the import.

NETWORK

The subordinate element <NETWORK> contains information on inter alia, transport systems, nodes, zones, links, and link types.

MATRICES

---

ROUTING

The subordinate element <ROUTING> contains information on routes and volumes.

NETWORK

An *.anm file contains the superordinate XML element <NETWORK>.

 

ANM

Visum

LEFTHANDTRAFFIC

Left-hand traffic in network settings

The <NETWORK> element contains the following subordinate elements. The mapping of the subordinate elements to Visum objects is subsequently described in detail.

ANM

Visum

VEHTYPES

Determine the type of transport system (PuT, PrT) Each VEHTYPE is mapped to a demand segment.

VEHCLASSES

List of XmlAnmVehClass objects Each one is mapped to a transport system.

NODES

Are mapped to nodes

ZONES

Are mapped to zones

LINKTYPES

Are mapped to link types

LINKS

Are mapped to links

PTSTOPS

---

PTLINES

---

SIGNALCONTROLS

Are mapped as signal controllers

VEHCLASSES

The <VEHCLASSES> are mapped as follows:

ANM

Visum

VEHTYPEID

Code and name of the transport system

Note

Several VEHTYPES can belong to one VEHCLASS. For each VEHCLASS, Visum creates a transport system and a mode, for each VEHTYPE a demand segment. The transport system is allocated to the mode with the same name, and the mode is allocated to all demand segments created from the VEHTYPES contained in that VEHCLASS.

VEHTYPES

The <VEHTYPES> are mapped as follows:

ANM

Visum

NO

---

NAME

Code and name of the demand segment

VEHCATEGORY

Type of the transport system (of the corresponding VEHCLASS)

Note

If the first VEHTYPE of a VEHCLASS is bus or tram, the entire VEHCLASS is mapped as PuT. The categories of all further VEHTYPES of this VEHCLASS are ignored.

NODES

The <NODES> are mapped as follows:

Note: Main nodes are not inserted.

ANM

Visum

NO

Number of the node

NAME

Name of the node

XCOORD, YCOORD, ZCOORD

Coordinates of the node

CONTROLTYPE

Control type of the node

SBAMERGINGPENALTY SBA penalty for merging vehicles

IGNOREDIFF

---

NUMLANES

Number of lanes in roundabout for control type roundabout

TURNS

Turns

LANES

Lanes

LANETURNS

Lane turns

CROSSWALKS

Crosswalks

LANES

The lane information of a leg has to be consistent. The number of through lanes has to be the same as the Number of lanes in Visum.

The <LANES> are mapped as follows:

ANM

Visum

LINKID

Link number

INDEX

Lane numbers

POCKET

Determines if this is a pocket

Note

If it is a pocket, the corresponding origin lane has to be located on one of the sides of the pocket.

POCKETLENGTH

Indicates the length of the pocket

WIDTH

Width

BLOCKEDVEHICLECLASSES

Set of transport systems blocked on this lane

STOPLINEPOS

Leg\stop lines position

Note

The leg attribute is the average of the values of all the inbound lanes in Visum.

TRAFFICSIGN

Determines the major flow of the node

Note

If the traffic signs of a node are consistent, a manual major flow will be defined on the node.

If lanes are defined on a node, the information of the traffic signs of the lanes overwrites the information on the turns.

DETECTORS

Detectors that are allocated to the lane

DETECTORS

In ANM files, detectors can be allocated to crosswalks, lane turns and lanes. In Visum, detectors and lane turns cannot be connected directly. Here, detectors are connected to crosswalks or lanes. Only one detector can be allocated to a crosswalk. A lane can have several detectors. If a crosswalk with several detectors is read in, only the first detector will be read in.

The <DETECTORS> are a subordinate element of the <LANES>. They are mapped as follows:

ANM

Visum

TYPE

Type of the detector

SCNO

Number of the signal controller

PORTNO

Channel number

NAME

Name of the detector

POSOFFSET

Stop line distance

LENGTH

Detector length

AFFECTEDPTLINES

---

AFFECTEDVEHCLASSES

Transport system set of the detector

LANETURNS

The <LANETURNS> are an element of the <NODES>. They are mapped as follows:

ANM

Visum

FROMLINKID, FROMLANEINDEX, TOLINK-ID, TOLANEINDEX

From link number, From lane number, To link number and To lane number of the lane turn

BLOCKEDVEHCLASSES

Set of transport systems blocked on this lane turn

LANETURNPOLY

---

DETECTORS

Detectors on lane turns are not read in

SCNO

Number of the signal controller to which the signal group under <SGNO> is allocated

Note

The number has to be identical for all lane turns and crosswalks of a node.

SGNO

Signal group number

Note

The signal group belongs to the signal controller of the lane turn.

ORSGNO

Number of a second signal group

SIGNALTYPE

---

CROSSWALKS

Visum crosswalks are read in from the two ANM classes <CROSSWALKS> and <CROSSWALKSIDE>. In Visum a crosswalk is defined by the leg it belongs to, the direction and an index from 1 to 3. So there can be a maximum of six crosswalks belonging to one leg.

A <CROSSWALKSIDE> on the left side is mapped to a crosswalk with the direction "false" in Visum. On the right side, it has the value "true".

Note: As in Visum there can only be one crosswalk of each type, i.e. up to six all in all, it is possible that crosswalk data from the ANM model will be discarded during the import.

The <CROSSWALKS> are an element of the <NODES>. They are mapped as follows:

ANM

Visum

LEFTSIDE, RIGHTSIDE

References to the directions

INLINKID, OUTLINKID

Numbers of the links crossed by the crosswalk

CHANNELIZEDTURN

Indicates whether the crosswalk leads to a channelized turn

Note

The value can only be "true" if the leg\channelized turn length of the respective leg is unequal to zero.

SCNO

Defines the signal controller that is allocated to the node. The SCNO has to be the same for all lane turns and crosswalks on the node.

INDEX

---

WIDTH

Width

Note

If references to LEFTSIDE or RIGHTSIDE exist, the width of each of the two crosswalks is half the ANM width.

OFFSET

---

CROSSWALKSIDES

The <CROSSWALKSIDES> define the direction of the crosswalks. ANM crosswalks have two directions.

ANM

Visum

DETECTORS

Allocated detector

SGNO

Signal group

PEDVOL

Pedestrian volume

BIKEVOL

---

XCOORD, YCOORD

---

TURNS

The <TURNS> are a subordinate element of the <NODES>. The <TURNS> are mapped as follows:

ANM

Visum

BLOCKEDVEHICLECLASSES

Set of transport systems blocked on this turn

FROMLINKID, TOLINKID

From link number and To link number of the turn

TRAFFICSIGN

Determines the major flow of the node

Note

If the traffic signs of a node are consistent, a manual major flow will be defined on the node.

If lanes are defined on a node, the information of the traffic signs of the lanes overwrites the information on the turns.

ZONES

<ZONES> are mapped 1:1 as zones. ANM zones have no polygon. Therefore the generated Visum zones do not have polygons either.

ANM

Visum

NO

Number of the zone

XCOORD, YCOORD, ZCOORD

Coordinates of the zone

Note

The Z-Coordinates are not read in.

CONNECTORS

Connectors of the zone

CONNECTORS

The <CONNECTORS> are a subordinate element of the <ZONES>. They are mapped as follows:

ANM

Visum

BLOCKEDVEHCLASSES

Set of transport systems blocked on this connector.

NODENO

Node number

DIRECTION

Direction

Note

The direction indicates whether the connector leads towards zone or away from it. "False" means source, "true" means destination. In Visum each connector automatically has a reverse direction. If the reverse connector is not contained in the ANM file, the reverse direction is closed to all transport system in Visum.

LINKTYPES

The link type set in Visum is adapted by the import and the names of the link types are adopted.

ANM

Visum

NO

Link type number

NAME

Link type name

DRIVINGBEHAVIOUR

---

LINKS

<LINKS> are mapped as follows:

ANM

Visum

ID

Link number

Note

Visum tries to find a matching link number. It can be any string. If the ANM file was exported from Visum, the original numbers can be reallocated.

FROMNODENO, TONODENO

From node number, To node number

NAME

Name of the link

LINKTYPENO

Link type number

SPEED

v0 PrT

NUMLANES

Number of lanes

REVERSELINK

---

Note

The reverse direction is added automatically in Visum.

BLOCKEDVEHCLASSES

Set of transport systems blocked on this link

VEHCLASSSPEEDS

Maximum speed per vehicle class

Note

For each link, the minimum of v0 and v0(TSysSet) is exported for all PrT TSys of the TSysSet of the link.

LINKPOLY

Course of the link

Note

The link courses of the opposite directions in ANM may differ, in Visum they may not. If both courses have the same number of elements, the average of the coordinates will be used. If the number of elements is not the same, the course with the higher number of elements will be used.

TURNONRED

Turn on red permitted

TRIANGLEISLANDLENGTH

Is mapped to the inbound node leg of the associated link.

Note

The attribute Channelized turn length is defined on the leg in Visum.

SLO, ELO, SLOL, ELOL

These numbers determine the width and the length of the central island in Visum.

Note

SLO and ELO indicate the width, SLOL and ELOL indicate the length.

CLO

---

FROMNODERADIUS

Roundabout exit radius of the leg at the From node

Note

The attribute is defined at the leg in Visum.

TONODERADIUS

Roundabout exit radius of the leg at the To node

Note

The attribute is defined at the leg in Visum.

PTSTOPS and PTLINES

Public transit data is currently not imported.

SIGNALCONTROLS

The <SIGNALCONTROLS> are mapped as signal controllers as follows:

ANM

Visum

SIGNALGROUPS

Signal groups of the signal controller

INTERGREENS

Intergreens of the signal controller

NO

Number of the signal controller

NAME

Name of the signal controller

CYCLETIME

Cycle time of the signal controller

TIMEOFFSET

Offset of the signal controller

SIGNALIZATIONTYPE

Signaling type of the signal controller

Note

The type is determined by the ANM attribute Programfile.

CYCLETIMEFIXED

---

PROGRAMNO

Program number

PROGRAMFILE

Determines the signal control type in Visum

SIGNALPROGRAMDATA

Transfers the signal data of the signal controller

The data is imported into Vissim for fixed time controls.

SUPPLYFILE1

File name

SUPPLYFILE2, §

---

WTT1, 2, 3

---

SIGNALGROUPS

ANM

Visum

NO

Number of the signal group

NAME

Name of the signal group

GTSTART

Green time start

GTSTART2

---

GTEND

Green time end

GTEND2

---

RATIME

---

ATIME

---

MINGTIME

Minimum green time

MINRTIME

---

ALLRED

Allred

SIGNALGROUPTYPE

---

INTERGREENS

ANM

Visum

FROMSGNO, TOSGNO

From signal group, To signal group

INTERGREEN

Intergreen

Note

The value is added to the intergreen matrix of the signal controller.

ROUTING

If the ANM file contains routing information, the routes are assumed to consist of three nodes. These nodes are used to uniquely determine a Visum turn. No routes are created in Visum. Instead the given volumes are assigned to user-defined turn attributes per vehicle type.

ANM

Visum

VEHTYPETIS

Connects a time interval to an ANM VEHTYPEID

Note

An ANM VEHTYPEID is an element of an ANM VEHCLASS that is mapped to a transport system in Visum.

ROUTES

Turn volumes per transport system

VEHTYPETIS

ANM

Visum

INDEX

---

FROMTIME, TOTIME

---

VEHTYPEID

Determines the transport system of the route

ROUTES

The import only works for routes with exactly three items. The ANM nodes that the items refer to have to correspond to Visum nodes which uniquely define a Visum turn. That means that the first node and the third node have to be neighbors of the second node.

ANM

Visum

ITEMS

Pair consisting of a node and an optional link

DEMANDS

Can be defined for each Visum transport system. They are mapped to user-defined Visum turn attributes.

FROMZONENO, TOZONENO

---

INDEX

---